Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Static FIND cursor repositioning

With the DataServer, cursor repositioning will work with an ORACLE database the same as it does with the Progress 4GL, except when the ORACLE Database Manager fails to find a record. In the Progress 4GL, the cursor is located after the last record that was read. In ORACLE, a failed search does not affect the cursor. For example, if a cursor is positioned at cust-num 50 and a request to find customer “smith” in an ORACLE table fails, the cursor remains at cust-num 50. The same failed request from a Progress 4GL table places the cursor after the last customer read trying to find customer “smith”.

The DataServer repositions only cursors used by FIND NEXT/PREV/CURRENT statements. Cursors are never repositioned for FOR EACH statements, new queries, or dynamic FINDs. When the DataServer instructs the ORACLE RDBMS to perform a join (JOIN-BY-SQLDB), the cursor that the join uses does not reposition other cursors in use by the query. The cursor for DEFINE QUERY or dynamic FIND statements does not reposition cursors in other queries.